<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD 4.1 Release</title>
<link rev=made href="mailto:www@openbsd.org">
<meta name="resource-type" content="document">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="description" content="OpenBSD 4.1">
<meta name="keywords" content="openbsd,main">
<meta name="distribution" content="global">
<meta name="copyright" content="This document copyright 2007 by OpenBSD.">
</head>

<body bgcolor="#ffffff" text="#000000" link="#24248E">

<a href="index.html">
<img alt="[OpenBSD]" height="30" width="141" hspace="24" src="images/smalltitle.gif" border="0"></a>
<hr>

<p>
<a href="images/openbsd41_cover.gif">
<img align="left" width="227" height="343" hspace="24" vspace="30"
src="images/PuffyBaba.jpg" alt="OpenBSD 4.1 logo"></a>
<h2><font color="#0000e0">The OpenBSD 4.1 Release:</font></h2>
<p>
Released May 1, 2007<br>
Copyright 1997-2007, Theo de Raadt.<br>
<font color="#e00000">ISBN 978-0-9731791-9-4</font>
<br>
<a href="lyrics.html#41">4.1 Song: "Puffy Baba and the 40 Vendors"</a>
<p>

<a href="#new">What's New</a><br>
<a href="#install">How to install</a><br>
<a href="#upgrade">How to upgrade</a><br>
<a href="#ports">How to use the ports tree</a><br>
<a href="orders.html">Ordering a CD set</a><br>

<p>
<h3><font color="#0000e0">
To get the files for this release:
<ul>
<li>Order a CDROM from our <a href="orders.html">ordering system</a>.
<li>See the information on <a href="ftp.html">The FTP page</a> for
    a list of mirror machines.
<li>Go to the <font color="#e00000">pub/OpenBSD/4.1/</font> directory on
    one of the mirror sites.
<li>Briefly read the rest of this document.
<li>Have a look at <a href="errata41.html">The 4.1 Errata page</a> for a list
    of bugs and workarounds.
<li>See a <a href="plus41.html">detailed log of changes</a> between the
    4.0 and 4.1 releases.
</ul>
</font></h3>
<br clear=all>

<strong>Note:</strong> All applicable copyrights and credits can be found
in the applicable file sources found in the files src.tar.gz, sys.tar.gz,
XF4.tar.gz, or in the files fetched via ports.tar.gz.  The distribution
files used to build packages from the ports.tar.gz file are not included on
the CDROM because of lack of space.
<p>

<a name="new"></a>
<hr>
<p>
<h3><font color="#0000e0">What's New</font></h3>
<p>
This is a partial list of new features and systems included in OpenBSD 4.1.
For a comprehensive list, see the <a href="plus41.html">changelog</a> leading
to 4.1.
<p>

<ul>

<li>New/extended platforms:
<ul>
<li><a href="landisk.html">OpenBSD/landisk</a>.<br>
    Various SH4-based appliances, made by IO-Data and resold by Plextor.
<li><a href="sparc64.html">OpenBSD/sparc64</a>.<br>
    UltraSPARC III based machines are now supported even better, and
    run at full speed now!
</ul>
<p>

<li>Removed platforms:
<ul>
<li><a href="cats.html">OpenBSD/cats</a>.<br>
    Because the machines are very hard to find, and the developers
    hate them.
</ul>
<p>

<li>Improved hardware support, including:
<ul>
<li>New USB client controller support:
<ul>
<li>Support for the USB client functionality in the
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pxaudc&amp;sektion=4&amp;arch=zaurus">pxaudc(4)</a> driver on the Zaurus.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=usbf&amp;sektion=4">usbf(4)</a> midlayer for USB Client controllers.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cdcef&amp;sektion=4">cdcef(4)</a> driver for providing a CDCE function on USB client controllers.
</ul>
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cas&amp;sektion=4">cas(4)</a> driver for Sun Cassini 10/100/Gigabit Ethernet devices.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=uow&amp;sektion=4">uow(4)</a> driver for Maxim/Dallas DS2490 USB 1-Wire devices.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=owsbm&amp;sektion=4">owsbm(4)</a> driver for 1-Wire smart battery monitor devices.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=zyd&amp;sektion=4">zyd(4)</a> driver for ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless network devices.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=moscom&amp;sektion=4">moscom(4)</a> driver for MosChip Semiconductor MCS7703 based USB serial adapters.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=glxsb&amp;sektion=4&amp;arch=i386">glxsb(4)</a> driver for hardware random numbers and AES acceleration on the AMD Geode LX processor.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=vic&amp;sektion=4">vic(4)</a> driver for VMware VMXnet Virtual Interface Controllers.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=malo&amp;sektion=4">malo(4)</a> driver for  Marvell Libertas IEEE 802.11b/g wireless network devices.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pwdog&amp;sektion=4">pwdog(4)</a> driver for Quancom PWDOG1 watchdog timer devices.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=uberry&amp;sektion=4">uberry(4)</a> driver for Research In Motion Blackberry devices.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mbg&amp;sektion=4">mbg(4)</a> driver for Meinberg Funkuhren radio clocks.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mesh&amp;sektion=4&amp;arch=macppc">mesh(4)</a> driver for the on-board SCSI controller of old world Apple Power Macintosh systems.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mc&amp;sektion=4&amp;arch=macppc">mc(4)</a> driver for the on-board Ethernet of many old world Apple Power Macintosh systems
<li>Improved <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=msk&amp;sektion=4">msk(4)</a> driver now supports many more Marvell Yukon-2 variants including dual port cards and fiber cards.
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gem&amp;sektion=4">gem(4)</a> driver now supports fiber cards.
<li>The <a href="amd64.html">OpenBSD/amd64</a>
platform now has more accurate and robust time keeping.
<li>The <a href="i386.html">OpenBSD/i386</a>
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=boot&amp;sektion=8&amp;arch=i386">boot(8)</a>
program now works properly on Intel-based Macs.
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pciide&amp;sektion=4">pciide(4)</a> driver has had support added for newer chipsets, including:
<ul>
<li>AMD CS5536 IDE;
</li><li>Intel i31244;
</li><li>NVIDIA MCP67 PATA, MCP67 SATA.
</li></ul>
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=com&amp;sektion=4">com(4)</a> driver now supports ST16C654 devices.
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=adt&amp;sektion=4">adt(4)</a> driver supports some newer chipsets, such as the ADT7475.
<li>The <a href="macppc.html">OpenBSD/macppc</a> platform now automatically turns the machine back on following an unexpected loss of power.
<li>boot.mac an XCOFF formated boot loader for <a href="macppc.html">OpenBSD/macppc</a> capable of booting on many old world macs.
</ul>
<p>

<li>New tools:
<ul>
<li>BSD-licensed <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg-config&amp;sektion=1">pkg-config(1)</a>, a complete rewrite of the GNU tool of
the same name, significantly smaller and more maintainable. 
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=hoststated&amp;sektion=8">hoststated(8)</a>, a layer 3 and layer 7 server load balancing daemon with host monitoring capacities.
<li>new BSD-licensed <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ripd&sektion=8">ripd(8)</a>.
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bgplg&amp;sektion=8">bgplg(8)</a>, a CGI looking glass for OpenBGPD, is now available for use with the system httpd.
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bgplgsh&amp;sektion=8">bgplgsh(8)</a>, a looking glass shell for OpenBGPD, is now available for use as a restricted read-only command line interface.
</ul>
<p>

<li>New functionality:
<ul>
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=syslogd&amp;sektion=8">syslogd(8)</a>
    can now pipe logs directly to other programs, making real-time log analysis easier.
<li>The IP_RECVTTL
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ip&amp;sektion=4">ip(4)</a>
socket option allows programs to receive the incoming ttl on raw and udp sockets.
<li>The IP_MINTTL
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ip&amp;sektion=4">ip(4)</a>
socket option allows programs to ask the kernel to discard any packets with a ttl
smaller than the given one, for implementing the IP TTL security hack aka the Generalized
TTL Security Mechanism specified in RFC 3682.
<li>Multiple, independent routing tables, with 
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4">pf(4)</a>
acting as selector.
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=route&amp;sektion=8">route(8)</a>
can be told which table to work with now, and routing daemons have been modified to
cope as well.
<li>The
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflog&amp;sektion=4">pflog(4)</a>
interface is now clonable.
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4">pf(4)</a>
can log to multiple pflog interfaces now, each rule can specify which pflog interface
to log to.
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflogd&amp;sektion=8">pflogd(8)</a> and
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=spamlogd&amp;sektion=8">spamlogd(8)</a>
can now be told which pflog interface to work with.
<li>The
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfsync&amp;sektion=4">pfsync(4)</a>
interface is now clonable as well, thus only there when actually needed.
<li>
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8">pfctl(8)</a>
can now expire table entries.
<li><i>keep state</i> is now the default for <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5">pf.conf(5)</a> rules, as is the <i>flags S/SA</i> option on TCP connections. <i>no state</i> and <i>flags any</i> can be used to disable stateful filtering or TCP flags checking.
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8">pfctl(8)</a> ruleset optimiser can be enabled in <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5">pf.conf(5)</a>.
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4">pf(4)</a> anchors can now be loaded inline in the main <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5">pf.conf(5)</a> and can be printed recursively.
<li>Allow
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4">pf(4)</a>
    rules inside anchors to have their counters reset, and make counter read
    &amp; reset an atomic operation.
<li>
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sensorsd&amp;sektion=8">sensorsd(8)</a>
dampens status changes now, thus not alerting for a single wrong sensor read, since many
sensors lie once in a while.
<li>
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=spamd&amp;sektion=8">spamd(8)</a> and 
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=spamlogd&amp;sektion=8">spamlogd(8)</a> now support synchronisation of the greylist database across multiple hosts. The greytrapping mechanism now allows for whole domain traps, and noticing out of order MX use.
<li>
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=spamd&amp;sektion=8">spamd(8)</a> database format has changed from DB_BTREE to DB_HASH for much better performance on large installations with big databases.
<li>
The
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bridge&amp;sektion=4">bridge(4)</a> driver and the
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=brconfig&amp;sektion=8">brconfig(8)</a> tool now support
the Rapid Spanning Tree Protocol (RSTP).
The new RSTP mode is now used by default when enabled with the <em>stp</em> option.
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cd&amp;sektion=4">cd(4)</a> now supports reading from region protected DVDs.
<li>Detect
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mount_msdos&amp;sektion=8">MS-DOS filesystems</a>
and spoof disklabel partitions for them even when there is no MBR, e.g. on some newer iPods.
</ul>
<p>
<li>Assorted improvements and code cleanup:
<ul>
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=fsck_ffs&amp;sektion=8">fsck_ffs(8)</a>
command has been improved to be more robust to various forms of inode and
superblock corruption.
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=top&amp;sektion=1">top(1)</a>
command got some new ways of filtering the display.
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pthreads&amp;sektion=3">pthreads(3)</a>
file descriptor handling has been improved to eliminate several race and deadlock conditions and improve performance.
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mount_msdos&amp;sektion=8">MS-DOS filesystem</a>
has had a potential corruption issue fixed, and is more reliable when given
a corrupted filesystem to mount.
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mount_msdos&amp;sektion=8">MS-DOS filesystem</a>
and the
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=fdisk&sektion=8&arch=i386">fdisk(8)</a>
command have been enhanced to work on devices with 2048 byte sectors,
e.g. newer iPods.
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=rcs&amp;sektion=1">OpenRCS</a> tools
are smarter at handling files, especially when dealing with binary files.
GNU RCS compatibility has also been improved.
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mg&amp;sektion=1">mg(1)</a>
editor now displays column numbers in the status bar.  It has also
received several improvements which make it more reliable: line
numbers, file insertions, and search wrapping all now work as
expected.
<li>The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=systat&amp;sektion=1">systat(1)</a>
command has a cleaner look, and a display was added for hardware sensors.
<li>The <a href="alpha.html">OpenBSD/alpha</a> platform now uses gcc3.
<li>Improved support for usb attached cd drives and ever more odd
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=umass&amp;sektion=4">umass(4)</a>
devices.
<li>Don't treat NetBSD or FreeBSD MBR partitions as substitutes for an OpenBSD partition. i.e. don't try to boot from them or use them to store OpenBSD disklabels.
</ul>
<p>

<li>Install/Upgrade process changes:
<ul>
<li>More reliable detection of disk and cd devices.
<li>More reliable installation from MSDOS FAT partitions.
<li>New sanity check in case sets for the wrong architecture are selected.
<li>No need to specify the filesystem types of source partitions during disk
    or cd installs.
<li>No need to select a source partition during disk or cd installs when
    there is only one to choose from.
</ul>
<p>

<li>OpenBGPD 4.1:
<ul>
<li>Fixes for sessions with tcp md5sig and ipsec. Now sessions can be migrated
    from and to any form of ipsec and tcpmd5 with just a simple
    <em>bgpctl reload</em>, and the session migrates the next time it gets
    established.
<li>Include file support in the config parser.
<li>Can now use the new IP_MINTTL socket option to implement the ttl security
    mechanism.
</ul>
<p>

<li>OpenOSPFD 4.1:
<ul>
<li>Reload support added. It is no longer needed to restart ospfd after a
    configuration change.
<li>Multiple networks per interface are now supported.
<li>It is now possible to specify the route metric and type for each
    redistribution rule.
</ul>
<p>

<li>OpenNTPD 4.1:
<ul>
<li>Greatly improved support for timedelta sensors.
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ntpd&amp;sektion=8">ntpd</a>
    now uses a strictly monotonically increasing time (uptime, basically)
    for its internal timers, so setting the system clock doesn't influence
    query rates, trust levels, etc. any more.
</ul>
<p>

<li>OpenSSH 4.6:
<ul>
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sshd&amp;sektion=8">sshd</a>
    now allows the enabling and disabling of authentication
    methods on a per user, group, host and network basis via the
    <em>Match</em> directive in 
    <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sshd_config&amp;sektion=5">sshd_config(5)</a>.
</ul>
<p>

<li>Over 4200 ports, 4000 pre-built packages (for i386), minor robustness improvements 
in package tools. Some highlights:
<ul>
<li>gstreamer-0.10 tools.
<li>OpenOffice.org package, available through ftp for size reasons.
<li>KDE 3.5.6 and koffice 1.6.2.
<li>a large (&gt; 500) number of new/updated perl modules, from CPAN, including
most of the catalyst web framework.
<li>NetBeans 5.5 Java IDE.
<li>updated Linux emulation support by using Fedora Core libraries.
<li>Mozilla Firefox 2.0.0.2 (with translations).
<li>PostgreSQL 8.2.3.
</ul>
<p>

<li>As usual, steady improvements in manual pages and other documentation.
<p>

<li>The system includes the following major components from outside suppliers:
<ul>
<li>X.Org 6.9.0 (+ patches, and i386 contains XFree86 3.3.6 servers
(+ patches) for legacy chipsets not supported by X.Org)
<li>Gcc 2.95.3
(+ <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gcc-local&amp;sektion=1">patches</a>)
and 3.3.5
(+ <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gcc-local&amp;sektion=1">patches</a>)
<li>Perl 5.8.8 (+ patches)
<li>our improved and secured version of Apache 1.3, with SSL/TLS and DSO support
<li>OpenSSL 0.9.7j (+ patches)
<li>Groff 1.15
<li>Sendmail 8.14.0, with libmilter
<li>Bind 9.3.4 (+ patches)
<li>Lynx 2.8.5rel.4 with HTTPS and IPv6 support (+ patches)
<li>Sudo 1.6.8p9
<li>Ncurses 5.2
<li>Latest KAME IPv6
<li>Heimdal 0.7.2 (+ patches)
<li>Arla 0.35.7
<li>Binutils 2.15 (+ patches)
<li>Gdb 6.3 (+ patches)
</ul>
<p>

</ul>

<a name="install"></a>
<hr>
<p>
<h3><font color="#0000e0">How to install</font></h3>
<p>
Following this are the instructions which you would have on a piece of
paper if you had purchased a CDROM set instead of doing an alternate
form of install.  The instructions for doing an FTP (or other style
of) install are very similar; the CDROM instructions are left intact
so that you can see how much easier it would have been if you had
purchased a CDROM instead.
<p>

<hr>
Please refer to the following files on the three CDROMs or FTP mirror for
extensive details on how to install OpenBSD 4.1 on your machine:
<p>
<ul>
<li>CD1:4.1/i386/INSTALL.i386
<p>
<li>CD2:4.1/amd64/INSTALL.amd64
<li>CD2:4.1/macppc/INSTALL.macppc
<p>
<li>CD3:4.1/sparc/INSTALL.sparc
<li>CD3:4.1/sparc64/INSTALL.sparc64
<p>
<li>FTP:.../OpenBSD/4.1/alpha/INSTALL.alpha
<li>FTP:.../OpenBSD/4.1/armish/INSTALL.armish
<li>FTP:.../OpenBSD/4.1/hp300/INSTALL.hp300
<li>FTP:.../OpenBSD/4.1/hppa/INSTALL.hppa
<li>FTP:.../OpenBSD/4.1/landisk/INSTALL.landisk
<li>FTP:.../OpenBSD/4.1/luna88k/INSTALL.luna88k
<li>FTP:.../OpenBSD/4.1/mac68k/INSTALL.mac68k
<li>FTP:.../OpenBSD/4.1/mvme68k/INSTALL.mvme68k
<li>FTP:.../OpenBSD/4.1/mvme88k/INSTALL.mvme88k
<li>FTP:.../OpenBSD/4.1/sgi/INSTALL.sgi
<li>FTP:.../OpenBSD/4.1/vax/INSTALL.vax
<li>FTP:.../OpenBSD/4.1/zaurus/INSTALL.zaurus
</ul>
<hr>

<p>
Quick installer information for people familiar with OpenBSD, and the
use of the "disklabel -E" command.  If you are at all confused when
installing OpenBSD, read the relevant INSTALL.* file as listed above!
<p>

<h3><font color="#e00000">OpenBSD/i386:</font></h3>
<ul>
Play with your BIOS options to enable booting from a CD. The OpenBSD/i386
release is on CD1. If your BIOS does not support booting from CD, you will need
to create a boot floppy to install from. To create a boot floppy write
<i>CD1:4.1/i386/floppy41.fs</i> to a floppy and boot via the floppy drive.

<p>
Use <i>CD1:4.1/i386/floppyB41.fs</i> instead for greater SCSI controller
support, or <i>CD1:4.1/i386/floppyC41.fs</i> for better laptop support.

<p>
If you can't boot from a CD or a floppy disk,
you can install across the network using PXE as described in
the included INSTALL.i386 document.

<p>
If you are planning on dual booting OpenBSD with another OS, you will need to
read INSTALL.i386.

<p>
To make a boot floppy under MS-DOS, use the &quot;rawrite&quot; utility located
at <i>CD1:4.1/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS,
use the
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dd&amp;sektion=1">dd(1)</a>
utility. The following is an example usage of
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dd&amp;sektion=1">dd(1)</a>,
where the device could be &quot;floppy&quot;, &quot;rfd0c&quot;, or
&quot;rfd0a&quot;.

<ul><pre>
# <strong>dd if=&lt;file&gt; of=/dev/&lt;device&gt; bs=32k</strong>
</pre></ul>

<p>
Make sure you use properly formatted perfect floppies with NO BAD BLOCKS or
your install will most likely fail. For more information on creating a boot
floppy and installing OpenBSD/i386 please refer to
<a href="faq/faq4.html#MkFlop">FAQ 4.3.1</a>.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/amd64:</font></h3>
<ul>
The 4.1 release of OpenBSD/amd64 is located on CD2.
Boot from the CD to begin the install - you may need to adjust
your BIOS options first.
If you can't boot from the CD, you can create a boot floppy to install from.
To do this, write <i>CD2:4.1/amd64/floppy41.fs</i> to a floppy, then
boot from the floppy drive.

<p>
If you can't boot from a CD or a floppy disk,
you can install across the network using PXE as described in the included
INSTALL.amd64 document.

<p>
If you are planning to dual boot OpenBSD with another OS, you will need to
read INSTALL.amd64.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/macppc:</font></h3>
<ul>
Put CD2 in your CDROM drive and poweron your machine while holding down the
<i>C</i> key until the display turns on and shows <i>OpenBSD/macppc boot</i>.

<p>
Alternatively, at the Open Firmware prompt, enter <i>boot cd:,ofwboot
/4.1/macppc/bsd.rd</i>
</ul>

<p>
<h3><font color="#e00000">OpenBSD/sparc:</font></h3>
<ul>
The 4.1 release of OpenBSD/sparc is located on CD3. To boot off of this CD you
can use one of the two commands listed below, depending on the version of your
ROM.

<ul><pre>
ok <strong>boot cdrom 4.1/sparc/bsd.rd</strong>
or
&gt; <strong>b sd(0,6,0)4.1/sparc/bsd.rd</strong>
</pre></ul>

<p>
If your SPARC system does not have a CD drive, you can alternatively boot from floppy.
To do so you need to write <i>CD3:4.1/sparc/floppy41.fs</i> to a floppy.
For more information see <a href="faq/faq4.html#MkFlop">FAQ 4.3.1</a>.
To boot from the floppy use one of the two commands listed below,
depending on the version of your ROM.

<ul><pre>
ok <strong>boot floppy</strong>
or
&gt; <strong>b fd()</strong>
</pre></ul>

<p>
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
will most likely fail.

<p>
If your SPARC system doesn't have a floppy drive nor a CD drive, you can either
setup a bootable tape, or install via network, as told in the
INSTALL.sparc file.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/sparc64:</font></h3>
<ul>
Put CD3 in your CDROM drive and type <i>boot cdrom</i>.

<p>
If this doesn't work, or if you don't have a CDROM drive, you can write
<i>CD3:4.1/sparc64/floppy41.fs</i> or <i>CD3:4.1/sparc64/floppyB41.fs</i>
(depending on your machine) to a floppy and boot it with <i>boot
floppy</i>. Refer to INSTALL.sparc64 for details.

<p>
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
will most likely fail.

<p>
You can also write <i>CD3:4.1/sparc64/miniroot41.fs</i> to the swap partition on
the disk and boot with <i>boot disk:b</i>.

<p>
If nothing works, you can boot over the network as described in INSTALL.sparc64.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/alpha:</font></h3>
<ul>
<p>Write <i>FTP:4.1/alpha/floppy41.fs</i> or
<i>FTP:4.1/alpha/floppyB41.fs</i> (depending on your machine) to a diskette and
enter <i>boot dva0</i>. Refer to INSTALL.alpha for more details.

<p>
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
will most likely fail.

</ul>

<p>
<h3><font color="#e00000">OpenBSD/armish:</font></h3>
<ul>
<p>
After connecting a serial port, Thecus can boot directly from the network
either tftp or http. Configure the network using fconfig, reset,
then load bsd.rd, see INSTALL.armish for specific details.
IOData HDL-G can only boot from an EXT-2 partition. Boot into linux
and copy 'boot' and bsd.rd into the first partition on wd0 (hda1)
then load and run bsd.rd, preserving the wd0i (hda1) ext2fs partition.
More details are available in INSTALL.armish.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/hp300:</font></h3>
<ul>
<p>
Boot over the network by following the instructions in INSTALL.hp300.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/hppa:</font></h3>
<ul>
<p>
Boot over the network by following the instructions in INSTALL.hppa or the
<a href="hppa.html#install">hppa platform page</a>.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/landisk:</font></h3>
<ul>
<p>
Write <i>CD3:4.1/landisk/miniroot41.fs</i> to the start of the CF
or disk, and boot normally.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/luna88k:</font></h3>
<ul>
<p>
Copy bsd.rd to a Mach or UniOS partition, and boot it from the PROM.
Alternatively, you can create a bootable tape and boot from it. Refer to
the instructions in INSTALL.luna88k for more details.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/mac68k:</font></h3>
<ul>
<p>
Boot MacOS as normal and extract the Macside "BSD/Mac68k Booter" utility from
<i>FTP:4.1/mac68k/utils</i> onto your hard disk.  Configure the "BSD/Mac68k
Booter" with the location of your bsd.rd kernel and boot into the installer.
Refer to the instructions in INSTALL.mac68k for more details.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/mvme68k:</font></h3>
<ul>
<p>
You can create a bootable installation tape or boot over the network.<br>
The network boot requires a MVME68K BUG version that supports the <i>NIOT</i>
and <i>NBO</i> debugger commands. Follow the instructions in INSTALL.mvme68k
for more details.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/mvme88k:</font></h3>
<ul>
<p>
You can create a bootable installation tape or boot over the network.<br>
The network boot requires a MVME88K BUG version that supports the <i>NIOT</i>
and <i>NBO</i> debugger commands. Follow the instructions in INSTALL.mvme88k
for more details.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/sgi:</font></h3>
<ul>
<p>
Burn cd41.iso on a CD-R, put it in the CD drive of your machine and
select <i>Install System Software</i> from the System Maintenance menu.

<p>
If your machine doesn't have a CD drive, you can
setup a DHCP/tftp network server, and boot using "bootp()/bsd.rd".
Refer to the instructions in INSTALL.sgi for more details.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/vax:</font></h3>
<ul>
Boot over the network via mopbooting as described in INSTALL.vax.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/zaurus:</font></h3>
<ul>
<p>
Using the Linux built-in graphical ipkg installer, install the
openbsd41_arm.ipk package.  Reboot, then run it.  Read INSTALL.zaurus
for a few important details.
</ul>

<p>
<h3><font color="#e00000">Notes about the source code:</font></h3>
<ul>
src.tar.gz contains a source archive starting at /usr/src.  This file
contains everything you need except for the kernel sources, which are
in a separate archive.  To extract:
<p>
<ul><pre>
# <strong>mkdir -p /usr/src</strong>
# <strong>cd /usr/src</strong>
# <strong>tar xvfz /tmp/src.tar.gz</strong>
</pre></ul>
<p>
sys.tar.gz contains a source archive starting at /usr/src/sys.
This file contains all the kernel sources you need to rebuild kernels.
To extract:
<p>
<ul><pre>
# <strong>mkdir -p /usr/src/sys</strong>
# <strong>cd /usr/src</strong>
# <strong>tar xvfz /tmp/sys.tar.gz</strong>
</pre></ul>
<p>
Both of these trees are a regular CVS checkout.  Using these trees it
is possible to get a head-start on using the anoncvs servers as
described <a href="anoncvs.html">here</a>.
Using these files
results in a much faster initial CVS update than you could expect from
a fresh checkout of the full OpenBSD source tree.
<p>
</ul>

<a name="upgrade"></a>
<hr>
<p>
<h3><font color="#0000e0">How to upgrade</font></h3>
<p>
If you already have an OpenBSD 4.0 system, and do not want to reinstall,
upgrade instructions and advice can be found in the
<a href="faq/upgrade41.html">Upgrade Guide</a>.

<a name="ports"></a>
<hr>
<p>
<h3><font color="#0000e0">Ports Tree</font></h3>
<p>
A ports tree archive is also provided.  To extract:
<p>
<ul><pre>
# <strong>cd /usr</strong>
# <strong>tar xvfz /tmp/ports.tar.gz</strong>
# <strong>cd ports</strong>
</pre></ul>
<p>
The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree.  Go
read the <a href="ports.html">ports</a> page
if you know nothing about ports
at this point.  This text is not a manual of how to use ports.
Rather, it is a set of notes meant to kickstart the user on the
OpenBSD ports system.
<p>
The <i>ports/</i> directory represents a CVS (see the manpage for
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&amp;apropos=0&amp;sektion=1&amp;manpath=OpenBSD+Current&amp;arch=i386&amp;format=html">
cvs(1)</a> if
you aren't familiar with CVS) checkout of our ports.  As with our complete
source tree, our ports tree is available via anoncvs.  So, in
order to keep current with it, you must make the <i>ports/</i> tree
available on a read-write medium and update the tree with a command
like:
<p>
<ul><pre>
# <strong>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_4_1</strong>
</pre></ul>
<p>
[Of course, you must replace the local directory and server name here
with the location of your ports collection and a nearby anoncvs
server.]
<p>
Note that most ports are available as packages through FTP. Updated
packages for the 4.1 release will be made available if problems arise.
<p>
If you're interested in seeing a port added, would like to help out, or just
would like to know more, the mailing list ports@openbsd.org is a good
place to know.
<p>

<hr>
<a href="index.html"><img height="24" width="24" src="back.gif" border="0"
alt="OpenBSD"></a>
<a href="mailto:www@openbsd.org">www@openbsd.org</a>
<br><small>
$OpenBSD: 41.html,v 1.91 2007/05/01 16:04:26 jj Exp $
</small>

</body>
</html>
